To identify the frequency of each outcome, you can:
use Oracle Policy Modeling's what-if analysis to bulk process the data, and then use Excel's native data analysis tools (eg sorting, filtering, statistical analysis) to analyze the outcomes, or
use the batch processor to bulk process the data, and then use another BI tool to analyze the outcomes.
This could be useful for seeing if any of the test cases result in unusual outcomes (eg outliers or negative results) which would point to errors in the rules. This process could also be used to identify each unique outcome.
Identify conflicting outcomes
To identify if two rules are ever true at the same time, you can:
Create a rule that tests if the offending combination of logic is true. For example,
there is an error in the rulebase if
the person is male and
the person is pregnant
Run the test cases, through the batch processor or as test scripts in Oracle Policy Modeling, to identify if the rule is ever true.
This could be useful for identifying double payments or conflicting outcomes.
Identify used and unused rules and conditions
To identify which rules and conditions are used and which are unused you can use the Test Script Coverage report. In this report:
rules and conditions are shown to be unused if zero percent are covered by the test suite. This is shown in the report by a 0 out of X at the relevant level, and by greyed out rules/conditions in the bottom pane.
rules and conditions are shown to be used if more than zero percent are covered by the test suite. This is shown in the report by at least 1 out of X at the relevant level, and by bolded 'true/false' values against conditions or by 'used' against conditionless rules.